Skip to main content

This is a new service – your feedback will help us to improve it.

London Borough of Lambeth

Article 4 direction area

There is a problem

  • permitted-development-rights column is missing values

STOCKWELL PARK

reference
A4D3A1
name
STOCKWELL PARK
article-4-direction
A4D3
permitted-development-rights

permitted-development-rights missing

uprns
address-texts
geometry
MULTIPOLYGON (((-0.116832 51.471713,-0.117430 51.471659,-0.117408 51.471570,-0.117610 51.471545,-0.117828 51.471526,-0.117825 51.471518,-0.117993 51.471498,-0.117929 51.471358,-0.117886 51.471290,-0.117794 51.471151,-0.117747 51.471088,-0.117656 51.470990,-0.117629 51.470964,-0.117601 51.470940,-0.117543 51.470898,-0.117499 51.470871,-0.117469 51.470855,-0.117429 51.470837,-0.117347 51.470803,-0.117268 51.470776,-0.117180 51.470750,-0.117032 51.470716,-0.117072 51.470781,-0.116800 51.470807,-0.116800 51.470811,-0.116597 51.470830,-0.116756 51.471449,-0.116822 51.471714,-0.116832 51.471713)),((-0.116923 51.470577,-0.116936 51.470580,-0.116965 51.470583,-0.117048 51.470596,-0.117174 51.470624,-0.117243 51.470646,-0.117301 51.470662,-0.117396 51.470693,-0.117438 51.470709,-0.117617 51.470784,-0.117614 51.470785,-0.117697 51.470840,-0.117817 51.470940,-0.117864 51.470993,-0.117907 51.471048,-0.118008 51.471191,-0.118076 51.471301,-0.118111 51.471362,-0.118158 51.471457,-0.118286 51.471439,-0.118349 51.471434,-0.118651 51.471429,-0.118556 51.471288,-0.118348 51.470988,-0.118267 51.470877,-0.118203 51.470783,-0.118111 51.470655,-0.118089 51.470622,-0.117860 51.470303,-0.117792 51.470321,-0.117404 51.470288,-0.117037 51.470288,-0.117033 51.470333,-0.117031 51.470381,-0.116923 51.470577)),((-0.116248 51.472814,-0.116535 51.472775,-0.116617 51.472762,-0.116645 51.472755,-0.116654 51.472746,-0.116661 51.472719,-0.116675 51.472688,-0.116720 51.472598,-0.116788 51.472510,-0.116800 51.472492,-0.116812 51.472470,-0.116822 51.472440,-0.116822 51.472428,-0.116736 51.472081,-0.116689 51.471906,-0.115989 51.471968,-0.116018 51.472056,-0.116043 51.472126,-0.116083 51.472226,-0.116125 51.472322,-0.116174 51.472513,-0.116248 51.472814)),((-0.116886 51.471962,-0.117007 51.472433,-0.117025 51.472509,-0.117028 51.472514,-0.117038 51.472519,-0.117048 51.472521,-0.117072 51.472520,-0.117351 51.472401,-0.117607 51.472289,-0.117788 51.472194,-0.117922 51.472092,-0.118010 51.471981,-0.118057 51.471832,-0.118057 51.471789,-0.118054 51.471745,-0.117512 51.471795,-0.117530 51.471899,-0.116886 51.471962)),((-0.115933 51.471171,-0.116491 51.471121,-0.116471 51.471041,-0.116446 51.470950,-0.116343 51.470544,-0.116145 51.470564,-0.116038 51.470581,-0.116064 51.470696,-0.115825 51.470716,-0.115894 51.470999,-0.115904 51.471034,-0.115933 51.471171)),((-0.117679 51.472883,-0.117724 51.472864,-0.117889 51.472781,-0.118073 51.472691,-0.118016 51.472645,-0.117962 51.472604,-0.118258 51.472442,-0.117937 51.472253,-0.117862 51.472300,-0.117772 51.472349,-0.117328 51.472543,-0.117373 51.472589,-0.117440 51.472651,-0.117679 51.472883)),((-0.116767 51.470565,-0.116766 51.470520,-0.116746 51.470443,-0.116744 51.470442,-0.116745 51.470438,-0.116741 51.470407,-0.116914 51.470389,-0.116905 51.470276,-0.116858 51.470179,-0.116838 51.470169,-0.116825 51.470170,-0.116451 51.470258,-0.116519 51.470514,-0.116529 51.470526,-0.116552 51.470536,-0.116588 51.470544,-0.116710 51.470561,-0.116767 51.470565)))
point
POINT (-0.117204 51.471478)
notes
entry-date
2024-07-11
start-date
1975-05-12
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve London Borough of Lambeth’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL